removed leading slash for tf frames to avoid problems with tf2 migration #818
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
see here for some related information: http://wiki.ros.org/tf2/Migration#Removal_of_support_for_tf_prefix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see here for some related information:
http://wiki.ros.org/tf2/Migration#Removal_of_support_for_tf_prefix
The problem became obvious when we migrated from kinetic to melodic, where we ran into errors from the ROS navigation stack (move_base), I assume they also migrated from tf to tf2, which was causing those issues.
I tried to find all places in the source base that have a leading slash and corrected it.